Skip to content

test(sbom-monitor): add Dragonfly user journey acceptance test#6870

Open
jacek-rzrz wants to merge 1 commit into
mainfrom
test/osf-422/sbom-monitor-dragonfly-user-journey
Open

test(sbom-monitor): add Dragonfly user journey acceptance test#6870
jacek-rzrz wants to merge 1 commit into
mainfrom
test/osf-422/sbom-monitor-dragonfly-user-journey

Conversation

@jacek-rzrz

Copy link
Copy Markdown
Contributor

Adds a real-server acceptance test for the SBOM monitor Dragonfly flow (INTERNAL_SNYK_CLI_ROLLOUT_DFLY_SBOM_MONITOR), following the same pattern as the existing sbom test reachability user journey test — no fake server, runs against the real Snyk API using process.env credentials.

Also renames all-projects.spec.tsbeta-all-projects.spec.ts to distinguish the mocked-server beta tests from this new user journey suite.

Relates to OSF-422.

@snyk-io

snyk-io Bot commented Jun 1, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@jacek-rzrz jacek-rzrz force-pushed the test/osf-422/sbom-monitor-dragonfly-user-journey branch from f10685a to 1bb1a19 Compare June 16, 2026 11:43
@jacek-rzrz jacek-rzrz force-pushed the test/osf-422/sbom-monitor-dragonfly-user-journey branch 3 times, most recently from 807544c to e2d7136 Compare June 23, 2026 15:17
@jacek-rzrz jacek-rzrz marked this pull request as ready for review June 23, 2026 15:18
@jacek-rzrz jacek-rzrz requested a review from a team as a code owner June 23, 2026 15:18
@jacek-rzrz jacek-rzrz force-pushed the test/osf-422/sbom-monitor-dragonfly-user-journey branch from e2d7136 to 69a578d Compare June 23, 2026 15:18
@snyk-pr-review-bot

This comment has been minimized.

@jacek-rzrz jacek-rzrz force-pushed the test/osf-422/sbom-monitor-dragonfly-user-journey branch from 69a578d to 96680a4 Compare June 23, 2026 15:21
@snyk-pr-review-bot

This comment has been minimized.

@snyk-pr-review-bot

This comment has been minimized.

@jacek-rzrz jacek-rzrz force-pushed the test/osf-422/sbom-monitor-dragonfly-user-journey branch from 96680a4 to 91c54a4 Compare June 23, 2026 15:52
@snyk-pr-review-bot

This comment has been minimized.

@jacek-rzrz jacek-rzrz force-pushed the test/osf-422/sbom-monitor-dragonfly-user-journey branch from 91c54a4 to e49f18c Compare July 9, 2026 15:21
@snyk-pr-review-bot

This comment has been minimized.


describe('snyk sbom monitor', () => {
it('should successfully monitor an SBOM', async () => {
const command = `sbom test --report --experimental --file=${SBOM_FILE_PATH} --asset-name=${ASSET_NAME}`;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Critical Bug: Wrong command is being executed

The test is intended to test snyk sbom monitor (per the file name, describe block, test name, and PR description), but the command actually executes sbom test instead:

const command = `sbom test --report --experimental --file=${SBOM_FILE_PATH} --asset-name=${ASSET_NAME}`;

This should be:

const command = `sbom monitor --experimental --file=${SBOM_FILE_PATH} --asset-name=${ASSET_NAME}`;

The --report flag is not needed for sbom monitor as monitoring inherently reports to the server. This bug causes the test to validate the wrong CLI functionality entirely, making it fail to test the Dragonfly SBOM monitor flow as intended.

Suggested change
const command = `sbom test --report --experimental --file=${SBOM_FILE_PATH} --asset-name=${ASSET_NAME}`;
const command = `sbom monitor --experimental --file=${SBOM_FILE_PATH} --asset-name=${ASSET_NAME}`;

Spotted by Graphite

Fix in Graphite


Is this helpful? React 👍 or 👎 to let us know.

Co-authored-by: Jacek Rzeniewicz <jacek@rzrz.pl>
Co-authored-by: Sara Regan <sara.regan@snyk.io>
Co-authored-by: Oana Andrisoaei <oana.andrisoaei@snyk.io>
@jacek-rzrz jacek-rzrz force-pushed the test/osf-422/sbom-monitor-dragonfly-user-journey branch from e49f18c to 9541f8e Compare July 10, 2026 14:38
@snyk-pr-review-bot

Copy link
Copy Markdown

PR Reviewer Guide 🔍

🧪 PR contains tests
🔒 No security concerns identified
⚡ No major issues detected
📚 Repository Context Analyzed

This review considered 3 relevant code sections from 3 files (average relevance: 1.00)

🤖 Repository instructions applied (from AGENTS.md)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant